Skip to main content
This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

HCL Notes/Domino 8.5 Forum (includes Notes Traveler)

Previous Next

While there are a number of factors that underly performance...

the results you are describing are not consistent with IBM's measurements.

Let me describe a couple of considerations and data points that are necessary to fully understood your context.

An initial open of a database, either locally or on a server, can take longer since the physical database information will not be present in the OS's disk cache. A subsequent open will be faster since it will often be cached by the OS and/or by the Domino server.

Opening a database for the first time (or after switching between releases), can also take some additional time. For the 1st open, view/folder indexes need to be rebuilt to ones that are compatible with the release. Subsequent opens can and will use the new indexes.

If a database was not properly closed, then a database fixup will often need to run to ensure the integrity of the database. The time required for a fixup is generally proportional to the size of the database. If the client is not closing properly, then it is possible that fixup is being run on the database at its next use.

Your description of minutes to open a database, consistently, is at least an order of magnitude off from our mail and calendar measurements, both for 1st open and subsequent open.


If the client is not closing all of its processes on shutdown, there may be a deadlock situation. Information to determine the problem can be collected as described below. The same steps below can be used to collect information to troubleshoot the database open.
Hide details for Collecting data for a hangCollecting data for a hang
Collecting data for a hang
If the Notes Client is unresponsive, and remains unresponsive, it may be hung.

To determine the root cause of the hang, an NSD and Java core file need to be generated.
To do so, perform the following steps:
1.        Open a DOS command prompt
2.        Switch to the Notes data directory
3.        Run ..\NSD                (no args, assuming that the program dir is "above" the data directory
4.        After the NSD completes, supply these 2 files, or do an ISA data collection
      1.        data\IBM_TECHNICAL_SUPPORT\nsd*.txt file
      2.        data\workspace\logs\java*.txt file                        "Java core"

    Since the problem is happening on a released version of the product, I encourage you open a report with Support to determine the underlying problem.


    Doug Conmy
    Lotus Notes Lead Architect
    IBM Senior Technical Staff Member


    Feedback response number DCOY7Q7HGB created by ~Dan Elwezenynds on 03/16/2009

    Performance Lotus Notes 8.5 (~Arnold Elnuson... 16.Mar.09)
    . . Performance Lotus Notes 8.5 (~Anita Zekluvit... 16.Mar.09)
    . . While there are a number of factors... (~Naomi Dwoachek... 16.Mar.09)
    . . . . Performance (~Arnold Elnuson... 17.Mar.09)




    Printer-friendly

    Search this forum

    Member Tools


    RSS Feeds

     RSS feedsRSS
    All forum posts RSS
    All main topics RSS